3 research outputs found

    Insight Into Africa’s Country-level Latencies

    Get PDF
    This paper provides insight into the effects of cross-border infrastructure and logical interconnections in Africa on both intra-country and cross-border latency on end-to-end Internet paths, by comparing Internet performance measurements between different countries. We collected ICMPpings between countries using Speedchecker and applied a community detection algorithm to group countries based on round trip times (RTTs) between countries. We observed three main latency clusters: East and Southern Africa; North Africa; and West and Central Africa. An interesting observation is that these clusters largely correspond to countries that share the same official languages or past colonial history. The cluster in Eastern and Southern Africa is the most strongly clustered: these countries have the lowest inter-country latency values. We also found that some countries have a much higher intra-country latency than expected, pointing to the lack of local peering or physical infrastructure within the country itself. This finding underscores the importance of physical networking infrastructure deployment and inter-network relationships at country and regional leve

    A First Look At Mobile Internet Use in Township Communities in South Africa

    Get PDF
    This paper presents a study of mobile data usage in South African townships. In contrast to previous studies, which have studied mobile data usage in developing regions (including South Africa), we focus our study on two townships in South Africa; the extremely resource-constrained nature of townships sheds light, for the first time, on how people in these communities use mobile data. We perform a mixed-methods study, combining quantitative network measurements of mobile app usage with qualitative survey data to gain insights about mobile data usage patterns and the underlying reasons for user behavior concerning mobile data usage. Due to the limited availability of public free Wi-Fi and despite the relatively high cost of mobile data, we find that a typical township user's median mobile data usage is significantly more than Wi-Fi usage. As expected, and consistent with observations of mobile data usage in parts of South Africa with better resources, users tend to favor using Wi-Fi for streaming video applications, such as YouTube. Interestingly, however, unlike users in less resource-constrained settings, township users also consume significant mobile data to update mobile applications, as opposed to relying on Wi-Fi networks for application updates. These behaviors suggest that network and mobile application designers must pay more attention to data usage patterns on cellular networks to provide mobile network architectures that provide more cost-effective mechanisms for tasks such as application update

    On the potential of Google AMP to promote local content in developing regions

    Get PDF
    The Google Accelerated Mobile Pages (AMP) project has gained lot of interest from content providers as a means to improve user experience. It introduces a number of innovations to streamline the downloading, parsing and rendering of pages. Google recently announced the hosting of more than 2B+ web pages, covering more than 900K domains. Due to the constrained nature of Internet connectivity in developing regions, AMP offers particularly exciting potential for improving web user experience in these countries. This paper provides a first look at Google’s AMP performance in Africa. We start by outlining the current web infrastructure provisioning in Africa, using local news websites as a case study. Discovering a sparse and low performance environment, we then evaluate the benefits that AMP can introduce in terms of accessibility to local content in developing regions. This study reveals that in Africa, AMP is able to reduce page load time and page size by a factor of 3 and 8 respectively. However, AMP is not a neutral technology as the search engine favours content that is using Google AMP. This raises an important question of search neutrality
    corecore